Disaster scenario based inferential analysis using feedback for extracting and combining cyber risk information

ABSTRACT

Various embodiments of the present technology include methods of assessing risk of a cyber security failure in a computer network of an entity. Some embodiments include generating a disaster scenario that includes elements of a disaster event, modeling the disaster scenario against a profile of the computer network and the entity, determining theoretical damage based on the modeling, and updating a cyber security policy or a network change to mitigate the theoretical damage.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of co-pending U.S. patent application Ser. No. 15/374,212, entitled DISASTER SCENARIO BASED INFERENTIAL ANALYSIS USING FEEDBACK FOR EXTRACTING AND COMBINING CYBER RISK INFORMATION filed Dec. 9, 2016 which is a continuation-in-part of U.S. patent application Ser. No. 15/141,779, entitled INFERENTIAL ANALYSIS USING FEEDBACK FOR EXTRACTING AND COMBINING CYBER RISK INFORMATION filed Apr. 28, 2016, which is a continuation-in-part of U.S. patent application Ser. No. 14/931,510, entitled DIVERSITY ANALYSIS WITH ACTIONABLE FEEDBACK METHODOLOGIES filed Nov. 3, 2015, now U.S. Pat. No. 9,373,144 which is a continuation-in-part of U.S. patent application Ser. No. 14/585,051, entitled DIVERSITY ANALYSIS WITH ACTIONABLE FEEDBACK METHODOLOGIES filed Dec. 29, 2014, now U.S. Pat. No. 9,253,203. All of the above applications are hereby incorporated by reference herein in their entirety including all references cited therein. U.S. patent application Ser. No. 15/141,779 is also a continuation-in-part of International Application No. PCT/US2015/067968, entitled SYSTEM FOR CYBER INSURANCE POLICY INCLUDING CYBER RISK ASSESSMENT/MANAGEMENT SERVICE filed Dec. 29, 2015, which is an international application of U.S. patent application Ser. No. 14/614,897, entitled SYSTEM FOR CYBER INSURANCE POLICY INCLUDING CYBER RISK ASSESSMENT/MANAGEMENT SERVICE filed Feb. 5, 2015, which claims the benefit of U.S. Provisional Patent Application No. 62/098,238, entitled SYSTEM FOR CYBER INSURANCE POLICY INCLUDING CYBER RISK filed Dec. 30, 2014. All of the above applications are hereby incorporated by reference herein in their entirety including all references cited therein.

FIELD OF THE PRESENT TECHNOLOGY

The present technology relates generally to systems and methods for determining metrics, such as diversity or similarity, between entities and the application of those metrics as actionable feedback loops which can be used to increase diversity or reduce similarity amongst groups of entities. These metrics may relate to diversity of aggregate cyber security risk for use in planning or filtering new entities so as to increase that diversity.

SUMMARY

Various embodiments of the present technology include a method comprising assessing risk of a cyber security failure in a computer network of an entity, using a computer agent configured to collect information from at least publicly accessible Internet elements. In some embodiments of the present technology, the assessing of risk includes evaluating the collected information to obtain circumstantial or indirect information that is indicative of the entity and cross referencing data in the collected information to confirm or infer that the entity is referenced in the circumstantial or indirect information that is indicative of the entity being referenced in the circumstantial or indirect information. Various embodiments include at least one of increasing or decreasing the assessed risk if the circumstantial or indirect information is negative or positive. Various embodiments also include automatically determining, based on the assessed risk, a change or a setting to at least one element of policy criteria of a cyber security policy, automatically recommending, based on the assessed risk, computer network changes to reduce the assessed risk, and providing one or more recommended computer network changes to reduce the assessed risk.

Various embodiments of the present technology further include generating a disaster scenario that includes elements of a disaster event, modeling the disaster scenario against a profile of the computer network and the entity, determining theoretical damage based on the modeling, and updating the cyber security policy or a network change to mitigate the theoretical damage.

Various embodiments of the present technology further include enactment by the entity of at least one of the one or more of the recommended computer network changes to reduce the assessed risk to the entity, determining that the entity has enacted at least a portion of the recommended computer network changes, and in response, automatically reassessing the risk of a cyber security failure in the computer network of the entity based on the enacted recommended computer network changes. Various embodiments of the present technology also include dynamically re-determining, based on the reassessed risk of a cyber security failure in the computer network of the entity, the change or the setting to the at least one element of policy criteria of the cyber security policy.

Various embodiments of the present technology further include any of using outcome data of the modeling by incorporating the same into the re-determining of the risk of a cyber security failure in the computer network. In some embodiments, a disaster scenario is based on selections from an end user and the elements are used as a portion of the collected information used in the risk assessment. Example methods include generating recommended suggestions for the computer network relative to the disaster scenario and based on the collected information obtained for the computer network and the entity, as well as generating optimized or improved disaster scenarios based on outcomes of disaster scenario modeling of a plurality of computer networks.

BRIEF DESCRIPTION OF THE DRAWINGS

Certain embodiments of the present technology are illustrated by the accompanying figures. It will be understood that the figures are not necessarily to scale and that details not necessary for an understanding of the technology or that render other details difficult to perceive may be omitted. It will be understood that the technology is not necessarily limited to the particular embodiments illustrated herein.

FIG. 1 is a high level schematic diagram of computing architecture for practicing aspects of the present technology.

FIG. 2 is a flowchart of an example method for determining entity diversity.

FIG. 3 is a flowchart of an example action and feedback loop method for updating a diversity score and improving client diversity.

FIG. 4 is a flowchart of a method for analyzing a new client's impact on an existing diversity calculation.

FIG. 5 is a block diagram illustrating a device according to an example embodiment.

FIG. 6 is an example graphical user interface (GUI) that comprises a graphical representation that plots an entity's motivation and sophistication relative to cyber risk.

FIG. 7 is an example graphical user interface (GUI) that comprises a scatter plot illustrating an entity's motivation and sophistication relative to cyber risk.

FIG. 8 is an example graphical user interface (GUI) that comprises a bar graph illustrating the plotting of a plurality of entities based on their combination scores.

FIG. 9 is an example graphical user interface (GUI) that comprises a bar graph illustrating the plotting of a plurality of entities based on their sophistication scores.

FIG. 10 is an example graphical user interface (GUI) that comprises a bar graph illustrating the plotting of a plurality of entities based on their motivation scores.

FIG. 11 is an example graphical user interface (GUI) that comprises a scatter plot that represents a plurality of entities plotted according to their combination score.

FIG. 12 is an example graphical user interface (GUI) that comprises a scatter plot that represents a plurality of entities plotted according to their combination score, as well as additional graphical representations for an entity and a list of recommendations based on the plotting.

FIG. 13 is a flowchart of an example method of the present technology.

FIG. 14 is a flowchart of another example method of the present technology.

FIG. 15 is a flowchart of yet another example method of the present technology.

FIG. 16 is a flowchart of an additional example method of the present disclosure.

FIGS. 17A and 17B collectively are a flowchart of an example method that incorporates disaster scenario based analyses and modeling of computing networks.

FIG. 18 is a schematic diagram of a computing system that is used to implement embodiments according to the present technology.

DETAILED DESCRIPTION

Various embodiments of the present technology are directed to systems and methods for determining diversity and/or similarity between entities with respect to risk, (e.g., cyber security risk), and the utilization of these metrics in various ways to improve diversity between the analyzed entities. In one embodiment, an insurer may desire to understand the diversity of their insured entities with respect to aggregate cyber risk and utilize a measure of diversity to prevent too much similarity between insured entities, and/or to compare their diversity to their industry peers. Additionally, reinsurers, rating agencies and/or insurance brokers may also utilize the present technology. For example, reinsurers may want to compare one insurer's portfolio to another insurer's to buy, invest, and/or cover. Brokers may wish to review their portfolio of clients, and ratings agencies may review an insurer's portfolio and use it to provide a rating on the financial strength rating of the insurer. To be sure, cyber insurance and other insurance risks can be a function of similarity. For cyber insurance risk, if insured entities are very similar to one another in a variety of key attributes such as revenue, clientele, industry, technology utilized such as cloud computing service provider, content delivery network (CDN) provider, operating system, firewall vendor, intrusion detection system vendor, security services provider, etc., or other factors, a loss, (e.g., due to a cyber attack), by one of these insured entities might imply that other insured entities having similar attributes will also experience a loss. For example, a plurality of web hosting provider may source their servers from the same company. A cyber attack of that company's servers may equally affect all of these web hosting providers that use the server, and consequently affect an insured that utilizes one of those web hosting providers to host the insured's website and other web services.

To be sure, diversity in attributes between entities can decrease the likelihood that a covered loss by any particular entity will also likely affect the other entities. Thus, the desire is to have the insured entities be as diverse as possible in the aggregate, to reduce overall risk. Conversely, similarity of attributes between insured entities can increase risk for the insurer.

Using the present technology, an end user may determine similar attributes shared between pluralities of entities. These shared attributes can be aggregated into clusters to locate groups of entities with shared attributes. In one example, several entities use the same content delivery network (CDN), the same cloud service provider, a similar website traffic profile, have overlapping executives, and report similar revenue. While these entities may also share attributes with other entities, these attributes are used in various embodiments to create a cluster or grouping of entities that, when considered in the aggregate, have a low diversity score due to the similarities in this example.

End users may use the present technology to learn their aggregate cyber risk compared to industry peers and use that information to, for example, screen potential target entities for inclusion into a group based upon how the potential addition of their attributes to the group would affect the diversity score for the end user's collection of entities. In alternative exemplary embodiments, the system may instead of, or in addition to, outputting a diversity or clustering score, may output a different value analyzing the entities, for example a probable maximum loss (PML) and/or an expected portfolio value.

The present technology can be used to analyze diversity/similarity between many entities. The diversity/similarity analyses can use hundreds and even thousands of attributes, looking for diversity or commonality therebetween. In some instances, the end user can adjust the attributes and/or select which attributes are important to them and the system will analyze only these attributes when determining diversity, (e.g., a diversity score for aggregate cyber risk).

While the examples above mention the suitability of the present technology for use with insurance planning, in general, and cyber insurance planning, in particular, the present technology is not so limited. Other examples of technologies that can implement the present technology are financial portfolio managers, technology companies that desire infrastructure robustness, human resources, venture capital investment, and so forth.

These and other advantages of the present technology are provided below with reference to the collective drawings.

FIG. 1 is a high level schematic diagram of a computing architecture (hereinafter architecture 100) of the present technology. The architecture 100 comprises a diversity analysis system 105 (hereinafter also referred to as system 105), which in some embodiments comprises a server or cloud-based computing device configured specifically to perform the diversity analyses described herein. That is, the system 105 is a particular purpose computing device that is specifically designed and programmed (e.g., configured or adapted) to perform any of the methods described herein.

The system 105 can be coupled with end user device 105A, such as computer, tablet, Smartphone, or other similar end user computing device. End users can interact with the system 105 using their end user device 105A. The end user device 105A and system 105 can be coupled using a network 105B.

A suitable network 105B may include or interface with any one or more of, for instance, a local intranet, a PAN (Personal Area Network), a LAN (Local Area Network), a WAN (Wide Area Network), a MAN (Metropolitan Area Network), a virtual private network (VPN), a storage area network (SAN), a frame relay connection, an Advanced Intelligent Network (AIN) connection, a synchronous optical network (SONET) connection, a digital T1, T3, E1 or E3 line, Digital Data Service (DDS) connection, DSL (Digital Subscriber Line) connection, an Ethernet connection, an ISDN (Integrated Services Digital Network) line, a dial-up port such as a V.90, V.34 or V.34bis analog modem connection, a cable modem, an ATM (Asynchronous Transfer Mode) connection, or an FDDI (Fiber Distributed Data Interface) or CDDI (Copper Distributed Data Interface) connection. Furthermore, communications may also include links to any of a variety of wireless networks, including WAP (Wireless Application Protocol), GPRS (General Packet Radio Service), GSM (Global System for Mobile Communication), CDMA (Code Division Multiple Access) or TDMA (Time Division Multiple Access), cellular phone networks, GPS (Global Positioning System), CDPD (cellular digital packet data), RIM (Research in Motion, Limited) duplex paging network, Bluetooth radio, or an IEEE 802.11-based radio frequency network.

In one embodiment, the system 105 comprises a processor 110 and memory 115 for storing instructions. The memory 115 can include an attribute module 120, a comparator module 125, a clustering module 130, a weighting module 135 and a recommendation module 140. As used herein, the terms “module” may also refer to any of an application-specific integrated circuit (“ASIC”), an electronic circuit, a processor (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.

For context, the diversity analyses according to various embodiments of the present technology begin with input for the attribute module 120. A set of variables that are indicative of attributes of an entity may be input into the attribute module 120. In one embodiment, the variables can include technologies a company might employ (e.g., internally and externally for Internet communication such as e-mail, website, and social media online presence) such as CDN provider, cloud service provider, server type, OS type, visitor traffic knowledge, customer profiles, as well as other non-technical information such as revenue, number of employees, years in business, and so forth. In various embodiments, the breadth and type of variables that can be analyzed and correlated are unlimited. In some embodiments, the breadth and type of variables that can be analyzed and correlated for the company and for their industry peers, for comparision, may be limited by breadth and type of information that is available at online sources concerning the same. Again, an end user can define or specify the types of variables that are of interest to them.

For example, if the end user is an insurer, the insurer may desire to know how diverse their insured entities are with respect to cyber security risk relative to a wide and divergent set of variables. In regard to a cloud computing provider, for example, interest in such diversity may be only in technological variables such as traffic, page views, bandwidth, and other variables related to cyber risk.

In some embodiments, entities and end users can access and interact with the system 105 using a variety of graphical user interfaces (GUIs) such as a dashboard, including various elements as described herein. The system 105 can use the dashboard to display messages or notifications as well as diversity scores, similarity scores, and/or recommendations.

The system may gather variables for an entity by querying the entity for information, collect information from available online sources such as websites, corporate filings, news sources, other public record databases and resources. Additionally, data may be gathered from the entity's network using devices already present there or by placing a new device on the entity's network to gather more data. The data collecting device may be a server, router, firewall, switch, or repeater, or may be a software agent or routine that monitors traffic and/or performs packet inspection. The data collecting device may be on the company's network and/or its periphery, and may collect and/or analyze the data, while also transmitting it to system 105. In this manner, additional, proprietary data may be gleaned from a particular entity's network. Regardless of how the variables are obtained, the variables are input into the attribute module 120. The attribute module 120 can format or normalize the input as needed for consistency.

In one embodiment, the comparator module 125 is executed to perform a variable comparison on all or a subset of the variables. The comparison can be for all or only a subset of all entities. The subset of variables can be selected by the end user, as well as the entities analyzed.

The comparator module 125 is configured to identify variables shared between entities or groups of entities. The implications of this analysis are multifaceted. For instance, the same variable can be shared between many entities, which leads to an inference that a particular variable might be problematic. This lack of diversity is a more pointed or granular lack of diversity.

In another example, multiple variables are shared between numerous entities. This diversity relationship between the entities signifies a more prolific lack of diversity.

Localized commonality can be found between small groups (even between two) entities. This type of similarity can be inferred as less problematic than the more prolific examples provided above where similarity exists between numerous entities.

The comparator module 125 can cooperate with the clustering module 130 to create commonality clusters (e.g., various clusters of commonly shared variables). In one embodiment, if five entities are being analyzed, many different clusters can be identified. By example, if variables A-D are being analyzed with respect to entities 1-5, the comparator module 125 finds commonality between entities 1 and 3 with respect to variables B and C. Also, the comparator module 125 finds commonality between entities 1-5 with respect to variable A. Other similar correlations can be found.

The clustering module 130 can display to the end user these commonality clusters, which indicate areas of non-diversity. Also, these commonality clusters can be utilized by the recommendation module 140 to create action items for the end user that if enacted would change the diversity score. Details regarding the diversity score are found in greater detail below.

In some embodiments, the comparator module 125 creates a diversity score or index. This diversity score represents how dissimilar the analyzed group of entities is relative to one another in view of their variables.

The diversity score can include a percentage of the overall number of compared variables that are dissimilar to those that are shared. The diversity score can be represented variously as a fraction, a decimal, or a percentage, and may be included in the graphical user interface (e.g., dashboard.) Additionally, or alternatively, the diversity score may be normalized into a number within a user-defined, or predefined, range, similar to a credit score.

In some embodiments, the comparator module 125 can cooperate with the weighting module 135 to applying a weighting to one or more variables. In one embodiment, the weighting is selected by an end user such as an insurer. For example, an insurer determines that industry serviced, gross revenue, and customer country of origin are important variables to analyze, (e.g., for assessing individual and aggregate cyber risk.) For instance, if the insurer knows that gross revenue is very important to the calculation, the insurer can specify that the gross revenue variable is to be given greater importance in the analysis than other variables. In another example, the insurer can assign a weight to each variable based upon importance.

In some embodiments, the system can determine weightings and variables based on industry knowledge acquired, and use machine learning, big data and other “tools” to make an “educated” determination. For example, the weighting of variables can also be determined by the system 105 based on information such as actuarial data, industry practices, or other rules established by end users but which are intended to be applied by default. The selection of a weighting schema by the system 105 can be based on variables for the entities. For example, if the system 105 determines that the entities are all physicians, the system 105 can select weightings that are appropriate for medical practices or hospitals. Such determinations by the system may be adjusted and/or otherwise specified by the end user (e.g., using the dashboard) to tailor them for their particular circumstances, preferences, or other factors.

In some embodiments, the diversity score can be represented as a diversity graph that illustrates the connection between entities. Entities can be graphically connected based on commonality of variables between entities. For example, certain entities may be connected as being banks that present particularly enticing targets for cyber criminals and thus particular cyber risks.

In response to calculating a diversity and/or similarity score, the recommendation module 140 can be executed to provide the end user with some type of actionable feedback. For example, the recommendation module 140 can provide the end user one or more actions to the end user based on the diversity score and the clusters of similar variables. These one or more actions potentially increase the diversity score if enacted by the end user.

In one example, the recommendation module 140 can automatically identify variables, which if changed, would affect the diversity score. For example, if the entities are or utilize technology company service providers that use a particular CDN, the recommendation module 140 can output a recommendation that diversification in this area would be beneficial. The end user can alert the entities and encourage them to explore other options for CDNs. If the end user is an insurer, for example, the insurer can encourage this change by offering rate concessions to the insured entities. Various embodiments of the system thus may automatically provide the diversity score or other information to the end user regarding diversity, which the end user can utilize to encourage or effect various changes (e.g., via rate concession, screening of potential new entities, adjusting rates based on diversity, or other actions prompted by the system's determinations.) The diversity score might also be used to inform the insurer as to which polices should be renewed and which polices should not be renewed. For example, if a potential new (target) entity to add presents an unacceptable cyber risk, based on the diversity analysis, the insurer may choose not to provide the entity' policy or to provide the policy at a rate commensurate with the risk.

In another example, the recommendation module 140 can identify problematic common variables that negatively impact diversity scores. For example, the recommendation module 140 may identify shared infrastructure such as CDNs and cloud service providers as particularly problematic variables that are commonly shared between several entities. In some embodiments, the recommendation module 140 can also identify network traffic, network traffic patterns, firewalls, firewall policies that are commonly shared. Changing these shared variables would likely increase the diversity score for these entities. Conversely, the recommendation module 140 can determine key variables that if changed would negatively affect a diversity score. The recommendation module 140 can identify these variables to the end user as desirable.

Actions that could be taken in response to this information could include a project plan that specifies that the insurer is to find new customers that do not share these problematic variables. Likewise, the project plan could also or alternatively specify that the insurer is to find new customers that do share key positive variables.

In one example, an action includes the recommendation module 140 creating and providing the end user with a variable profile of a target entity that when added to the plurality of entities increases the diversity score. For example, the recommendation module 140 could create a profile for a prototypical new client that is in a different technology sector or a completely different industry sector. In another embodiment, the recommendation module 140 could create a profile for a prototypical new client that includes desirable variables, rather than merely a client that excludes certain disfavored variables.

In one embodiment, the recommendation module 140 can provide the end user with a list of entities of the plurality of entities that are lowering the diversity score. Again, as mentioned above, certain clusters of variables may be found in common between entities. Certain ones of these clusters may have more of a negative impact on the diversity score than others. For example, commonality between headquarters or domicile may have no impact on the diversity score, even if this variable is shared in common between several entities. On the other hand, commonality in gross revenue or average employee age may have a drastic impact on the diversity score for one reason or another. To be sure, commonality of a variable(s) does not always negatively affect the end user or the end user's business. In these instances the commonality can be ignored or weighted so as not to affect the calculated diversity score.

In another example, the recommendation module 140 can provide the end user with a list of entities of the plurality of entities that, if lost would lower the diversity score, which can prompt the end user to take action to avoid.

In another example, action the recommendation module 140 can compare a variable profile for a new entity to determine if the addition of the new entity to the analysis will negatively or positively impact the diversity score of the group.

For example, the attribute module 120 can receive a variable profile for a new entity and parse out the variables which are indicative of attributes of the new entity. This profile could include an application form, a survey, or any other content that is capable of conveying variables.

Next, the comparator module 125 adds a set of variables of the new entity to the comparison described above and repeats the calculation of the diversity score. The recommendation module 140 can alert the end user if the addition of the new entity decreases the diversity score. The recommendation module 140 can alert the end user if the addition of the new entity increases the diversity score as well.

In some embodiments, the recommendation module 140 updates the diversity score based on feedback received from the end user. For example, if the end user wants to view how the addition of a proposed new client will affect an existing diversity score, the profile for the new client is added to the system and the variables for the new client are processed and added to the comparison process. A new or updated diversity score is calculated and displayed to the end user.

The difference between the new diversity score and the old diversity score is expressed as a diversity delta. In some embodiments, the system 105 can apply thresholds to the diversity delta to determine if a proposed change to the entity grouping is sufficient to warrant the proposed change. For example, the system 105 may require at least a net change or diversity delta of 20%. Other percentages can also be utilized. The present technology provides information related to the updated information (the new diversity score), including differences (the amount of the change made in one or more updates, namely the delta), and trends (patterns over many time steps).

The present technology also provides attribution information when a diversity score changes. In particular, the methods and system indicate to a user why the score has changed, namely what exactly has changed in the underlying data sets to effect that higher level score change. In this manner, the systems and methods of the present technology provide detailed information to the user to identify the changed data, and thereby understand the positive and negative impacts of the user's actions on the diversity score.

The system 105 can also build an entity portfolio for an end user with knowledge gained from an analysis of variables for a plurality of entities. For instance, the system 105 can create a report that informs the end user as to how many and what type of entities a portfolio should have to be balanced in terms of diversity, (e.g., with respect to cyber risk.) For example, the report may indicate that an insurer should have a certain percentage of clients in the banking sector, a certain percentage in the technology sector, and a certain percentage in the medial industry. These sectors of the portfolio are deduced by comparing variables for various entities in a given industry that lead to a suitable diversity score.

It will be understood that the diversity score can be counterbalanced by other factors such as revenue for the end user. That is, an insurer may be more likely to accept a lower diversity score from a group of entities that pay higher premiums or a group of entities that is at least partially self-insured.

FIG. 2 is a flowchart of an example method 200 that is executed by the system (e.g. system 105), in accordance with the present technology. The method 200 includes the system 105 (for each of a plurality of entities), receiving 205 a set of variables that are indicative of attributes of an entity. These variables can include any number or type of variables that represent the attributes of the entity.

These variables are collected for numerous entities that may belong, in some embodiments, to a particular class or group. For example, the entities could include all employees in a company, all insured customers of an insurance agency, investors in a mutual fund, or other groups.

Next the method 200 includes the system 105 comparing 210 the sets of variables for the plurality of entities to each other, and locating 215 clusters of similar variables shared between two or more of the plurality of entities.

Next, the method 200 includes the system 105 clustering 220 common variables and identifying the entities that share the common variables. These clusters are indicative of non-diversity between these entities.

Next, the method 200 includes the system 105 calculating 225 a diversity score that represents how different the plurality of entities are to one another based on variables that are not shared between the plurality of entities. This diversity is directly related to the commonality discovered above. The more similar or commonly shared variables exist, the less diverse the entities are relative to one another, as a general rule. Again, as mentioned above, some variables will have little to no impact on diversity as dictated by weighting or variable selection by the end user. For example, if a commonly shared variable is not included in the diversity calculation by the end user the variable has no impact on the diversity score.

Next, the method 200 includes the system 105 receiving 230 feedback from an end user in response to providing the diversity score to the end user. Also, the method 200 includes the system 105 updating 235 the diversity score in response to the feedback.

Various types of feedback are contemplated and illustrated in FIG. 2. The feedback can take the form of a suggestion, option, report, or other output that is actionable by the end user. Exemplary methods and systems according to the present technology may also provide benchmarking over time. In this manner, an insurance company or other entity tracking aggregate cyber risk may track their diversity score over an adjustable time period, for example days, weeks, months, and/or years.

It will be understood that the methods illustrated in flowchart form are susceptible to execution in various forms such that not all steps may be required. In some instances, additional steps can be added. Some steps may be rephrased or replaced with other steps, in accordance with the claimed technology.

In FIG. 3, the flowchart illustrates the method 300 including the system 105 providing 305 the user with one or more actions/suggestions that to the end user based on the diversity score and the clusters of similar variables. These actions can potentially increase the diversity score if enacted by the end user.

In step 310, an action includes providing the end user with a variable profile of a target entity that when added to the plurality of entities increases the diversity score.

In step 315, an action includes providing the end user with a list of entities of the plurality of entities that are lowering the diversity score.

In step 320, an action includes providing the end user with a list of entities of the plurality of entities that, if lost, would lower the diversity score.

Regardless of the action taken (steps 310, 315, and/or 320), the feedback is used in calculating 325 an updated diversity score and delivering 330 the updated diversity score to the end user.

Again, these options are merely examples and are not intended to be limiting. These options can be provided individually or in combination, if desired.

FIG. 4 is a flowchart of a new entity analysis method 400. In the method 400, the system (e.g. system 105) is utilized to compare the variables of a new entity to an existing diversity analysis. For example, an insurer desires to determine how the addition of this new entity will affect the diversity of an existing client base. This aggregate risk analysis can be used to ensure that diversity is maintained or increased when a new client is added to an existing pool of clients.

The method 400 includes receiving 405 a variable profile for a new entity. The variable profile either includes a set of variables or a set of variables is deduced from the variable profile. As mentioned above, the variable profile can include an application form, a resume, a corporate filing such as a tax return, or any other document that includes attributes of an entity.

Next, the method 400 includes adding 410 the set of variables of the new entity to the variables of the previously analyzed entities and performing 415 an updated comparison of variables. Next, the method 400 includes generating 420 an updated diversity score calculation.

In some embodiments, the method 400 includes alerting 425 the end user if the addition of the new entity decreases (or increases) the diversity score. The end user can decided to accept or reject this new client based upon how the client affects the diversity score.

Advantageously, the present technology can be used in scenarios where diversity of clientele is desirous. The present technology can perform diversity analyses on potentially thousands of attributes across countless entities in ways that would be impossible to accomplish absent the use of the diversity analysis system. The diversity analyses of the present technology can bring clarity to business planning and project management, where integration of new clients/entities may affect the diversity of a current client base (either positively or negatively). Where diversification is desirable or required, the present technology provides a means for facilitating and maintaining this diversity in a way that is actionable and usable to the end user. That is, the present technology provides a way for end users to mitigate risk through diversification of their customer base or however diversity impacts their particular business or operations.

Various embodiments of systems and methods are provided for assessing and reducing cyber risks associated with companies or other entities. In various embodiments, a method comprises assessing risk of a cyber security failure in a computer network of an entity, using a computer agent configured to collect information from at least publicly accessible Internet elements. The cyber security failure may include a cyber attack and/or a privacy incident (including but not limited to an incident involving sensitive information), to name just a few. The computer agent may be further configured to collect and/or analyze information from the computer network of the entity.

The exemplary method includes automatically determining, based on the assessed risk, a change or a setting to at least one element of policy criteria of a cyber security policy. The cyber security policy may be a policy from an insurance company, a product warranty for first and/or third party costs that an entity purchases from one of a networking, security product, or services provider, to name a few. In various embodiments, the method includes automatically recommending, based on the assessed risk, computer network changes to reduce the assessed risk and providing one or more recommended computer network changes to reduce the assessed risk, enactment by the entity of at least one of the one or more of the recommended computer network changes to reduce the assessed risk to the entity. In some embodiments, the exemplary method includes determining that the entity has enacted at least a portion of the recommended computer network changes, and in response, and automatically reassessing the risk of a cyber security failure in the computer network of the entity based on the enacted recommended computer network changes. The exemplary method further includes dynamically re-determining, based on the reassessed risk of a cyber security failure in the computer network of the entity, the change or the setting to the at least one element of policy criteria of the cyber security policy. In various embodiments, the at least one element of policy criteria of the cyber security policy is a term and/or a condition. For example, a term and a condition may include a retention amount, a deductible, a premium, a coverage limit, a future valuation, a term length, and so forth.

Various embodiments of systems and methods are provided for calibrating cyber risks associated with commercial markets. In various embodiments, a method comprises assessing the risk of a cyber security failure in a computer network of a commercial market, using a computer agent configured to collect information from at least publicly accessible Internet elements. The cyber security failure may include a cyber attack and/or a privacy incident (including but not limited to an incident involving sensitive information), to name just a few. The computer agent may be further configured to collect and/or analyze information from the computer network of the commercial market. In some embodiments, the commercial market is insurance, corporate credit, small business loans, global equities, derivatives, or futures, to name just a few. In various embodiments, the policy is a policy from an insurance company, or a warranty, to name a few. In various embodiments, the method includes automatically recommending computer network changes to reduce the assessed risk; and automatically reassessing the cyber risk of the computer network of the commercial market based on the recommended computer network changes. In some embodiments, the entity is a commercial market for at least one of insurance, corporate credit, small business loans, global equities, derivatives, and futures. In various embodiments, the method includes calibrating cyber risks associated with the commercial market.

In some embodiments, the method includes, based on the assessing of risk of the cyber security failure in the computer network of the entity, plotting one or more features of the entity and other members of a peer group of the entity, the plotting being configured to visually illustrate the risk of a cyber security failure in the computer network of the entity; and the automatically recommending of computer network changes being based on the plotting. The plotting may be configured to visually illustrate the cyber risk of the entity.

In some embodiments, the method comprises determining a sophistication score of the entity with respect to cyber risk, which may be considered the quality of the defense with respect to repelling, defeating, or preventing a security failure. Sophistication scores may also be referred to as susceptibility scores.

In some embodiments, the method also comprises determining a motivation score of a hacker or other actor with respect to initiating one of a cyber security failure. A composite score may be created from the motivation score and the sophistication score.

The exemplary method and system may be used in a cyber policy market, and/or by a cyber policy provider providing policies. The cyber policy may include a cyber risk assessment/management service, which may provide feedback to one or both of the policy company and the insured entity, enabling the entity to determine how to reduce their cyber risk, and/or how they are positioned within their peer group and/or within a universe of companies with respect to their cyber risk. As used herein, the policy, including but not limited to a cyber policy, may be a policy from an insurance company or it could be a product warranty for first and/or third party costs that an entity purchases from a networking or security product or services provider.

Additionally, following the recommendations may enable the policy company to update and/or change policy criteria of a cyber security policy. In still further alternatives, the composite score of several or many entities may be aggregated and used by insurance companies, reinsurance companies, brokers and/or ratings agencies to understand and/or evaluate an aggregate risk and assess insurance premiums and/or reinsurance treaties and/or change or evaluate a credit rating. This is described in further detail above.

Also, as mentioned above, the composite store can include facets of creditworthiness, small business risk, and other commercial metrics of commercial risk.

Cyber insurance insures entities against damage and/or loss due to security failures (e.g., a cyber attack, a privacy incident). Assessing cyber risk can be a difficult task due to the volatility of the cyber environment. For example, a risk of a security failure such as a cyber attack lacks actuarial data since there is an active adversary behind cyber attacks, and past cyber attacks do not predict future cyber attacks. Better analysis of cyber risk, including the risk of security failures, and providing greater service to insurance companies and insured entities, is desirable

The technology disclosed herein provides a cyber risk assessment, and provides methods and systems for improving a cyber risk assessment, by, for instance, reducing a risk of a cyber attack, predicting the probability of a cyber attack, and/or determining the extent to which a cyber attack might cause damage. Exemplary methods plot the cyber risk within a peer group, which may be defined by industry, revenue, and/or any other appropriate metric. Various exemplary methods plot the cyber risk within the universe of companies, (e.g., universe of companies for which such cyber risk has been assessed. Exemplary methods assess risk in a plot using one feature. In other examples, multiple features may be plotted into a matrix.)

For those exemplary matrix embodiments, the assessment of risk is plotted with a two (or more) dimensional analysis, which may be plotted into a two by two matrix or graph, or in any appropriate alternative visualization method, particularly for greater than two dimensions. For example, the two dimensions may be characterized as 1) motivation (which may be synonymous or similar to offense, e.g., the motivation of a bad actor to attack an entity) and 2) sophistication (which may be synonymous or similar to defense, e.g., the sophistication of an entity to prevent and/or repel a cyber attack, or compel more responsible behavior from employees and associates to prevent a privacy event with respect to sensitive information). Alternative axes for the two dimensional analysis are also possible, for example, measurements other than motivation and sophistication. The system may output an estimated (or expected) commercial impact, which may encompass both the risk of a cyber attack, and the potential amount of damage caused by a cyber attack.

In addition to analyzing the cyber risk, the present technology may provide enhanced value by quantifying a cyber risk, thereby creating a market for it. Additionally, the present technology may provide a cyber risk management service tied to a cyber policy. A cyber policy (also referred to as a cyber insurance policy) as used herein includes any insurance policy covering any loss arising out of a security failure, including tangible and intangible property. The policy may cover both first party and third party losses arising out of any perils including a security failure. The policy may cover business interruption, loss of income, Director and Officer liability, information asset coverage, and extra expense coverage, or any other insured loss arising out of a security failure. A cyber policy as used herein includes security and privacy coverage, including regulatory coverage (e.g., FTC, Health Insurance Portability and Accountability Act (HIPPA)) covering fines and penalties, and defense costs and damages. The coverage provided by a cyber policy as used herein may provide for privacy breach coaches, forensic experts, a public relations campaign, cyber extortion, information asset recovery, business interruption (including for example, lost income, extra expenses, and/or all costs incurred but for the cyber security failure), or any other covered costs or losses.

Aspects of a cyber policy may be altered based on use of, and implementation of recommendations provided by, the cyber risk management service. These aspects may include any policy criteria of the policy. Elements of policy criteria include, for example, a retention amount, a deductible, a premium, coverage limits, future valuation, term length, or a term or condition of the policy.

The analysis may be a position on a graph, and may include a scatterplot of the peer group members, and/or a simple ranking amongst the peers. The analysis may be two (or more dimensional). Additionally or alternatively, the analysis may be resolved into a single composite score embodying the analysis. The plot may be changed to include more or fewer members of the peer group based on further variables of the peer group members, for instance, revenue, etc. The plot may include points for a universe of companies along with the points for the particular entity. For a two dimensional analysis example, each axis may be a function of many sub-variables, discussed herein as examples of motivation and sophistication. The sub-variables may be weighted equally, or differently, and the weighting may be static, dynamic, or customizable based on different analysis goals. Examples of motivation and sophistication elements will be described in greater detail below.

The exemplary assessment system may provide recommendations to an entity to improve their cyber risk assessment, by, for instance, reducing their cyber risk. This may be accomplished by various methods, including increasing the sophistication of the organization or entity, or decreasing the motivation of the attacker to go after this organization or entity. The recommendations may be specific and may impact one or both of the axes of the two dimensional risk analysis. Implementing the recommendations, which may be accomplished in some embodiments automatically, may reduce the risk of a cyber security failure.

Implementing the recommendations may impact an entity's relative position in their peer group, in a universe of companies, as well as any expected commercial impact of a security failure (e.g., a cyber attack, a privacy incident). Additionally, factors beyond the control of the company or entity, for instance, actions by the other peer group members, activity in the hacker community or vulnerabilities in software and/or hardware, may also impact both a relative risk analysis (e.g., impacting the company or entity's position in their peer group) and/or an absolute expected commercial loss. This change over time may be accessible and/or charted for trending information, which may be useful for planning and/or changing policy criteria (including the premium) for the policy. An entity may make a judgment of which recommendations to prioritize in implementation based on the different recommendations provided by the system to other members of their peer group. Examples of recommendations are illustrated in FIG. 12.

In some embodiments, the recommendations generated for an entity can be changed in comparison with other entities in a group. Thus, the system 505 can provide a first set of recommendations based solely on the motivation and/or sophistication (e.g., cyber risk) analysis for the entity.

In another example, the system 505 can generate a second set of recommendations based on a comparison of the cyber risk for the entity to the aggregate risk score for many entities. This second set of recommendations includes additional recommendations for the entity which are determined to improve the cyber risk of the entity.

In some embodiments, the system 505 can determine risk factors that are discrepant between the entity and another entity (or an aggregate group of entities) and highlight these recommendations as being unique for the entity. For example, if the entity is the only one out of a group of their peer entities that does not use a CDN (content delivery network), the system 505 can highlight this difference. These unique discrepancies can illustrate areas where the entity is particularly or uniquely vulnerable.

Stated otherwise, the system 505 identifies clusters of sophistication elements or motivation elements that are shared between two or more of the portfolio of entities. The clusters of sophistication elements or motivation elements being associated with an increase in cyber risk. The recommendations generated by the system 505 for an entity of the portfolio of entities will cause a decrease in the cyber risk if implemented.

In various embodiments, where scores are tracked over time, the system 505 can also be configured to periodically reassess the cyber risk of an entity. In some embodiments, the reassessment occurs after the entity has implemented one or more of the recommendations.

It may be advantageous for the entity to understand not only that a particular score was changed, but also what affected the change in score. Thus, the system 505 is configured to provide attribution for a score change, including verifiable data including time and attribution information. This attribution identifies/represents the underlying data set which affected the score change, and shows why, how much, and how the score changes.

By way of example, the entity, unbeknownst to them, has a dramatic increase in pageviews on their website. This increase in pageviews causes an increase in the motivation score for the entity. That is, the increase in pageviews indicates that a hacker might be more motivated to hack the entity's webpage because of its high traffic profile.

In some embodiments, the system 505 can be used to automatically institute changes on behalf of the entity that will decrease the likelihood that the entity will experience or be adversely affected by a security failure such as a cyber attack. These automatic changes occur based on the recommendations generated for the entity.

In one example, the system 505 can establish new content hosts for the content of the entity. The system 505 can inform the entity that diversity in content hosting can decrease the likelihood that all of the entity's content or user information will be exposed, as compared to if the content is stored in one centralized location. To be sure, the system 505 can be used to automatically change technical aspects of the entity, such as computing diversity, content distribution and delivery, and other technical attributes.

In some embodiments, the system 505 comprises a commercial estimator module 550 that is configured to estimate a commercial impact to the entity for a simulated security failure (e.g., a cyber attack, a privacy incident). Thus, the system 505 can execute theoretical or simulated security failures against a cyber profile of an entity. In one example, the cyber profile for an entity is determined from the various sophistication and motivation elements determined for the entity. The commercial estimator module 550 then calculates the effect of, for example, a distributed denial of service attack (DDoS) on the entity. To be sure, the simulated cyber attack in this example tests the sophistication of the entity and is affected by the motivation regarding the entity. The economic impact can include an economic impact to the entity itself, other entities that depend upon the entity, or combinations thereof. For example, a cyber security failure for a commercial institution, such as a DDoS attack, can cause direct economic impact on the institution from website downtime. The cyber security failure can also cause a commercial impact to the customers of the commercial institution if social security numbers, account numbers, or other sensitive consumer and/or personal information is stolen.

Additionally, implementing the recommendations, provided by the cyber risk management service for example, may be paired with changes to the policy criteria of a policy. For example, implementation of certain recommendations may be paired with automatic renewal, a consequent lower (or higher or otherwise changed) cyber risk policy premium, better coverage limits, better term length, future valuation and the like. For example, the change to the policy criteria of the policy may be implemented after the end of the term (e.g., 1, 3, 6 or 12 months, or any other appropriate term) of the current policy, or may trigger a renewal option at the lower premium rate immediately or on an accelerated basis. In this manner, a cooperative and constructive relationship may be achieved between insurers and insured-entities, thereby creating a positive feedback loop of improved cyber preparedness and lower/higher/changed premiums. As discussed previously, implementation of recommendations provided by the cyber risk management service may cause a change in any element of the policy criteria of a cyber policy. For example, if the sophistication of the entity is low, a higher deductible may be required, and vice versa. Additionally or alternatively, the type of coverage, a pricing or re-pricing, the amount of limits, an automatic renewal, and/or a renewal commitment, may change based on an increase or decrease in sophistication of the entity, and/or an increase or decrease in motivation of an attacker of the entity. Additionally, as recommendations are implemented, or other changes in the entity or the entity's situation, the motivation and sophistication, or other metrics, may change, and consequently a new analysis may be provided including new and/or changed recommendations for the entity.

Additionally or alternatively, the policy criteria of the policy itself may determine and/or change the weighting used in the system 505. In still further embodiments, a policy may affect the system 505 in other ways. In other words, the policy criteria of a policy may impact an assessment of a cyber risk, and/or an assessment service. For example, if a policy has a high deductible, the assessment service may not assess a motivation to initiate a security event. Various other options for having the policy criteria of a policy drive the type of assessment conducted are also possible.

The cyber risk management service as provided herein may include subjective evaluations, and may include vulnerability assessments, penetration testing, tabletop exercises, people services, risk engineering, and/or training exercises. Changes or renewed evaluations of any of these assessments may cause an increase or decrease in a sophistication of the entity, an increase or decrease in a motivation of an attacker of the entity, and/or a change in any other metric used to evaluate an entity. Any of these changes based on a new or revised assessment may cause a remediation service and/or a new or additional assessment service, to be implemented. Trends, averages and/or changes to an assessment or evaluation may impact policy criteria of a cyber security policy, as discussed herein.

Various embodiments of the present technology can be practiced with a local computer system, and/or a cloud-based system. FIG. 5 is a high level schematic diagram of a computing architecture (hereinafter architecture 500) of the present technology. The architecture 500 comprises a system 505, which in some embodiments comprises a server or cloud-based computing device configured specifically to perform the diversity analyses described herein. That is, the system 505 is a particular purpose computing device that is specifically designed and programmed (e.g., configured or adapted) to perform any of the methods described herein. The system 505 can be coupled with entity device 530 using a network 520.

In one embodiment, the system 505 comprises a processor 510 and memory 515 for storing instructions. The memory 515 can include a recommendation module 540. As used herein, the terms “module” may also refer to any of an application-specific integrated circuit (“ASIC”), an electronic circuit, a processor (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.

The system 505 may gather variables for an entity by querying the entity for information, collecting information from available online sources such as websites, corporate filings, news sources, other public record databases, and other resources. Additionally, data may be gathered from the entity's network using devices already present there or by placing a new device on the entity's network to gather more data. The data collecting device may be a server, router, firewall, switch, or repeater, or may be a software agent or routine that monitors traffic and/or performs packet inspection. The data collecting device may be on the company's network and/or its periphery, and may collect and/or analyze the data, while also transmitting it to system 505. In this manner, additional, proprietary data may be gleaned from a particular entity's network. The variables or a subset of the variables can be compared. The comparison can be for all or only a subset of all entities. The subset of variables can be selected by the end user, as well as the entities analyzed.

In some embodiments, the system 505 provides interfaces or adapters 505A-N that allow various resources to communicatively couple with the system 505. As an example, the system 505 can use an application program interface (API) or other communication interface. FIG. 5 illustrates example resources that can couple with the system 505. The system 505 can interrogate, for example, various databases such as corporate filings, news sources, and other public record databases. In another example, cloud services such as cloud storage and cloud computing environments. In general, a cloud-based computing environment is a resource that typically combines the computational power of a large grouping of processors and/or that combines the storage capacity of a large grouping of computer memories or storage devices. For example, systems that provide a cloud resource may be utilized exclusively by their owners; or such systems may be accessible to outside users who deploy applications within the computing infrastructure to obtain the benefit of large computational or storage resources. The cloud may be formed, for example, by a network of servers with each server (or at least a plurality thereof) providing processor and/or storage resources. These servers may manage workloads provided by multiple users (e.g., cloud resource customers or other users). Typically, each user may place workload demands upon the cloud that vary in real-time, sometimes dramatically. The nature and extent of these variations typically depend on the type of business associated with the user.

The system 505 may also couple with the Internet as well as data feeds such as RSS feeds or social networks. Email behaviors can also be identified by interrogating email servers or email repositories.

In some embodiments, the system 505 can use vulnerability assessments generated by the entity or a third party, such as a cyber-security firm.

In contrast with a vulnerability assessment, which is more technical in nature, the present technology can also consider non-technical or semi-technical aspects of an entity and how these elements impact the cyber vulnerability of the entity. For example, non-technical elements include, but are not limited to, company size, revenue, company location, company industry sector, as well as other elements which are described herein. The present technology provides benefits above and beyond a typical vulnerability assessment, providing users with a robust and comprehensive view of a company's (or multiple companies') overall cyber security risk.

In some embodiments, the system 505 can obtain sophistication information about entities from the following non-limiting list of sources or resources: (a) Framework; (b) Hosting/infrastructure; (c) Account management; (d) Authentication; (e) Authorization; (f) System vulnerability; (g) Ad/Partner integration; (h) Files/Directories/Links; and (i) Patching.

In some embodiments, the system 505 can obtain sophistication information about entities from the following non-limiting list of sources or resources: (a) Customer Reviews; (b) Employee reviews; (c) Traffic statistics; (d) Business events/news; (e) Corporate connections; (f) Business type; (g) Customer data; (h) Brand/Revenue; (i) Employee profiles; (j) Social Media/Blogs; (k) Industry/Products; (l) Data Types; and (m) Company/Subsidiary connections.

For purposes of context, facets or features relating the motivation regarding a security failure (e.g., motivation of some actor, such as a hacker, to attack an entity, to expose sensitive information, to name a few) as well as the sophistication of the entity in preventing or dealing with a cyber security event will be referred to herein as an element. Thus, there can be a plurality of types of sophistication elements and a plurality of types of motivation elements. The actor may be a hacker, employee, another entity, to name a few.

Examples of motivation elements include: visibility; value; hacker sentiment; employee sentiment; company sentiment; customer sentiment, and combinations thereof—just to name a few. Each of these motivation elements may be further subcategorized as follows. Visibility may include information and/or derived measures related to the traffic, usage, and activity related to an entity, including but not limited to the in-links; pageviews; duration; traffic; links; page rank; market value; daily (stock) trade volume; exporting/importing; and combinations thereof—just to name a few. Value includes: revenue; net income; total assets; employees; and combinations thereof—just to name a few. Hacker sentiment includes: emails; credit cards; foreign languages; etc., which can be gathered from hacker forums and/or discussion groups, chat rooms, dark web, or dark net forums, such as the Tor Network, Internet Relay Chat (IRC), and combinations thereof—just to name a few. Employee sentiment includes: career opportunities; work/life balance; compensation; and combinations thereof—just to name a few. Company sentiment includes: senior leadership ratings; overall company ratings; recommendations; etc. Customer sentiment includes: product ratings; service ratings, and combinations thereof—just to name a few.

The present technology determines a level of sophistication of the entity. Sophistication may be considered a measure of People, Process, and Technology. People indicates how security-aware the entities' employees, principals and/or members are. In particular, do the people associated with the entity understand the risks, are they competent in security, and combinations thereof. Process indicates whether procedures and/or policies have clear and enforceable terms, and clearly indicate what to do in case of various events, including attacks. Process also indicates whether training is provided to employees, third party contractors and/or service providers, indicates their level of expertise, and combinations thereof

Examples of sophistication elements include: hosting infrastructure; topology; vulnerability research; people; and combinations thereof—just to name a few. Hosting infrastructure includes; content distribution networks; shared hosting; cloud providers; etc. Topology includes: accessibility points; page layout; content on site; etc. Vulnerability research includes: CVEs (common vulnerabilities and exposures); patching; updating; default passwords; etc. People includes: chief information security officer (CISO); security team; skills; job postings; etc. In this manner, sophistication encompasses more than just vulnerability, and additionally includes people and processes that may impact a defensive posture of an entity.

Determining these variables may be a data gathering operation, which may be based on public information or a company's own data networks, as discussed herein. A cyber risk assessment, for instance a two by two (or higher order) graph, may be output, along with a composite score, a peer rank, an estimated commercial impact, and recommendations to decrease the cyber risk. These may all be output for each company assessed. All of these elements may be updated over time and in response to implementation of recommendations, thus, transforming the original data via the use of a particular computer.

In some embodiments, the system 505 is configured to evaluate each data point with respect to history, lineage, provenance (e.g., origin), source, time, entities and other details. The system 505 can then cleanse and standardize the data points. Examples of cleansing and standardizing using data normalization are described in greater detail below.

In some embodiments, the system 505 can use a canonical representation of the data points. As mentioned above, the system 505 can track entities and their attributes/elements over time. The system 505 is also configured to process rollups (e.g., summarizing the data along a dimension), aggregations, transforms, reductions, normalizations, deltas, as well as other types of data transformation or conversion processes that can also be used to convert the motivation/sophistication/combination elements into scores.

The system 505 then generates module-ready data for use with matrices of elements (motivation/sophistication) for one or more entities. In some embodiments, the system 505 then executes one or more models to generate scores, results, recommendations, delta values (changes in scores over time), as well as historical tracking of scores.

In some embodiments, the system 505 comprises a scoring and plotting module 535 that is generally configured to calculate sophistication scores, motivation scores, and combination scores; apply weighting to sophistication and/or motivation elements in various calculations; compare scores to threshold values; benchmark various scores over time; as well as other features described herein.

In a second set of functions, the scoring and plotting module 535 can create visual representations such as the graphs illustrated in FIGS. 6-12.

In one embodiment, the scoring and plotting module 535 is configured to calculate various scores for an entity. In another embodiment the scoring and plotting module 535 can calculate various scores for a plurality of entities. Again, these various scores can be calculated over time and utilized for benchmarking cyber security performance for an entity, or a group of entities that possess a particular attribute in common. For example, the scoring and plotting module 535 can calculate scores for groups of entities in an industry group, a geographical location, a company size, a technology sector, and so forth.

In an example calculation, the scoring and plotting module 535 is configured to calculate a motivation score for one or more entities. The scoring and plotting module 535 obtains motivation elements collected from the various resources and converts this information into a mathematical representation. In one embodiment, a motivation element of pageviews can be mathematically represented by comparing the pageviews of the entity to a set of thresholds. For context, the pageviews could be a pageview of a particular webpage or set of webpages. To be sure, the higher profile and more visited a website is, the more likely that it will be attractive to a hacker, especially if other motivation factors are present such as the entity being involved in commercial activities, just for example.

For purposes of obtaining a coherent scoring scheme, the scoring and plotting module 535 may normalize various elements to obtain mathematical values that are usable in an algorithm for scoring motivation or sophistication. By way of example, each of the set of thresholds is associated with a mathematical value. If the entity has pageviews in excess of 10,000 unique users in one day, the entity is given a score of five. If the entity has pageviews in excess of 100,000 unique users in one day, the entity is given a score of ten. If the entity has pageviews in excess of 200,000 unique users in one day, the entity is given a score of fifteen. Again, these are merely examples of possible ways to convert pageviews into a mathematical representation that can be combined with other mathematical representations of other motivation elements in order to create an overall motivation score.

In other examples, an employee sentiment can be represented mathematically as a percentage of positive versus negative comments from employees. In another example, negative employee behaviors, actions, or statements can be counted over time and compared to thresholds (in a method similar to that above with respect to pageviews).

Each of the motivation elements (if necessary) is converted into a mathematical representation. The ultimate motivation score can be calculated by taking a sum of each mathematical representation of motivation elements. In some embodiments, the motivation score can be a representation of one or a combination of many motivation elements.

In some embodiments, the system 505 can be configured to weight one or more of the elements in a score calculation. For example, if it is determined that certain elements are more likely to increase the likelihood of a security failure (e.g., a cyber attack, a privacy incident), these elements can be assigned a weight. In an example, the weight is applied by multiplying a mathematical representation of an element by a coefficient or factor. If an element value for pageviews is five, a weighting could include multiplying this number by a coefficient of 0.5, which reduces the impact of that value on the overall score. Increases in element values can also be achieved.

While the above examples reference motivation elements, the scoring and plotting module 535 is also configured to process sophistication elements to obtain sophistication scores. The exact details for converting sophistication/motivation elements into mathematical representations will vary according to the type of information included in the elements. To be sure, some types of elements such as pageviews and revenue are inherently more mathematical in their quantities, while other elements are more non-mathematical in nature such as employee or customer sentiment. For non-mathematical elements, users can develop suitable schemes or algorithms for converting or quantifying these elements into mathematical form.

According to some embodiments, the scoring and plotting module 535 can determine various facets of an entity or group of entities by comparing the motivation, sophistication, and/or combined scores of these entities. Answers to pertinent questions can be deduced or inferred from the comparison.

For example, in one embodiment, the scoring and plotting module 535 is configured to determine a position of an entity within an aggregate risk score of a portfolio of entities. Thus, the scoring and plotting module 535 has been used to calculate an aggregate risk score (motivation, sophistication, and/or combined) for numerous entities. In one embodiment, the scoring and plotting module 535 selects a plurality of motivation elements and analyzes these elements for each of a portfolio (plurality) of entities using the above examples as a guide for calculating motivation scores. In some embodiments, the same motivation elements are used for each entity.

The scoring and plotting module 535 can then determine where the entity lies within the group of scores. For example, out of 30 entities, a subject entity places 25th out of thirty.

The scoring and plotting module 535 can also be utilized to generate graphs and GUIs that display various scores in graphical format(s). For example, in FIG. 6, a graph with two axes is illustrated. The graph 600 comprises a vertical axis that is representative of motivation elements, and the horizontal axis is representative of sophistication elements. Indeed, this graph can be used to display information about a single entity or a plurality of entities.

In one embodiment, the motivation axis is delineated or stratified based on the type of content. Less important types of secure information are located towards the bottom of the axis, whereas more important types of information are located at the top part of the axis. In this embodiment, the lower part of the motivation axis references payment cards (e.g., credit cards) and other types of general consumer information. Above that is online crime such as phishing, malware, and other malicious behavior. Above online crime is IP theft and industrial espionage. At the top of the motivation axis are state secrets. To be sure, other categories of information types will lie somewhere along this axis, if not specifically mentioned. Furthermore, the axis can be defined by other types of information points. For example, an entity can structure their motivation axis to include information that they deal with, structured from least important to most important.

In the sophistication axis, which is the horizontal axis, hacker profiles are listed from left to right on the axis from a lowest impact actor type to a highest impact actor type. For example, actor types can include casual hackers, professional hackers, organized crime, and state actors. Each of these actor types has a different threat level associated therewith. The sophistication axis represents the strength or threat level that it takes to successfully hack the subject entity/entities.

FIG. 7 is an example graphical user interface (GUI) that comprises scatter plot illustrating an entity's motivation and sophistication relative to cyber risk. The scatter plot 700 comprises a vertical motivation axis and a horizontal sophistication axis. Each of the points plotted on the scatter plot 700 represent an entity. Again, these entities can be analyzed together because they are a part of an entity group (e.g., industry group, same geographical location, same company size, etc.).

FIG. 8 is an example graphical user interface (GUI) that comprises a bar graph illustrating the plotting of a plurality of entities based on their combination scores. The bar graph 800 comprises a vertical axis that represents a number of companies and a horizontal axis that represents combination scores for a set of entities. For example, most entities in the group have combination scores (sophistication and motivation) that fall within a score range of 51-60. Other groups of entities fall within other score ranges.

To be sure the system 505 can cause an elemental analysis of these similar scoring groups to identify what elements are shared between the entities, what elements are different, and so forth. Thus, the graphing of entities based on scores aids the system 505 in identifying groups of entities that require attention. For example, the entities in the score range of 31-40 are severely underperforming.

FIG. 9 is an example graphical user interface (GUI) that comprises a bar graph illustrating the plotting of a plurality of entities based on their sophistication scores. The bar graph 900 comprises a vertical axis that represents a number of companies and a horizontal axis that represents sophistication scores for a set of entities.

FIG. 10 is an example graphical user interface (GUI) that comprises a bar graph illustrating the plotting of a plurality of entities based on their motivation scores. The bar graph 1000 comprises a vertical axis that represents a number of companies and a horizontal axis that represents motivation scores for a set of entities.

By comparing these graphs illustrated in FIGS. 8-10, underperformance in sophistication and/or motivation can be quickly and easily determined, at least on a high level. Again, a more granular element analysis can be conducted when groups with underperforming sophistication/motivation scores are identified.

FIG. 11 is an example graphical user interface (GUI) that comprises a scatter plot that represents a plurality of entities plotted according to their combination score. The scatter plot 1100 includes a plurality of data points that each represents an entity. The scatter plot 1100 comprises a vertical axis that represents motivation and a horizontal axis that represents sophistication scores for a set of entities. The higher risk area on the plot is where the motivation to hack is high and the sophistication of the entity is low.

The system 505 can create a line 1105 of acceptable motivation/sophistication scores. Companies falling below this line 1105 have a suitable cyber risk profile, whereas companies above the line have an unsuitable cyber risk profile. These companies can be identified and analyzed in order to suggest recommendations for improving their cyber risk.

FIG. 12 is an example graphical user interface (GUI) 1200 that comprises a scatter plot that represents a plurality of entities plotted according to their combination score, as well as additional graphical representations for an entity and a list of recommendations based on the plotting. The scatter plot includes a line 1205 of acceptable motivation/sophistication scores.

The plot is similar to that of FIG. 11, with the addition of two graphical representations. For example, a linear slide 1220 displays the position of an entity within a peer group of entities. This same relationship position is illustrated in a gauge graph 1210.

In response to making a cyber risk assessment, the recommendation module 540 can be executed to provide the end user (or entity) with some type of actionable feedback. For example, the recommendation module 540 can provide the end user one or more actions to the end user based on the diversity score and the clusters of similar variables. This is described in further detail above. These one or more actions potentially decrease the cyber risk of the entity. In one example, the recommendation module 540 can automatically identify variables, which if changed, would affect the cyber risk assessment. In further exemplary embodiments, entities may agree to automatic implementation of recommendations in exchange for lower policy premiums.

As best illustrated in FIG. 12, a set of recommendations 1215 is provided along with the graphical analysis generated for the entity. Again, these recommendations are based on the system 505 having knowledge of the motivation elements, sophistication elements, as well as the scores calculated not only for the entity, but other entities (in some embodiments).

Exemplary methods and systems according to the present technology may also provide benchmarking over time. In this manner, the system 505 can track, for a company or group or entities, cyber risk over a selectable time period, for example days, weeks, months, and/or years. This benchmarking may be against a dynamic or static evaluation of the peer group, for instance, an entity's past and present cyber risk tracked against a static past peer group, static present peer group, and/or dynamic peer group. The present technology provides information related to the updated information (the new motivation score, the new sophistication score, the new composite score, etc.), including differences (the amount of the change made in one or more updates, namely the delta), and trends (patterns over many time steps).

FIG. 13 is a flowchart of an example method 1300 of the present technology. The method 1300 includes the system 505 assessing 1305 risk of a cyber security failure in a computer network of an entity, using a computer agent configured to collect information from at least publicly accessible Internet elements. The cyber risk includes a security failure (e.g., a cyber attack, a privacy incident) of the entity.

The system 505 may query the entity for information, collect information from available online sources such as websites, corporate filings, news sources, other public record databases, and other resources. Additionally, data may be gathered from the entity's network using devices already present there or by placing a new data collecting device on the entity's network to gather more data. The data collecting device may be on the company's network and/or its periphery, and may collect and/or analyze the data, while also transmitting it to the system 505. In this example, additional, proprietary data may be gleaned from a particular entity's network.

The exemplary method 1300 also includes the system 505 automatically determining 1310, based on the assessed risk, a change or a setting to at least one element of policy criteria of a cyber security policy. In some embodiments, the at least one element of policy criteria involves a term or condition of a cyber policy. In one embodiment, the cyber security policy includes a cyber security insurance policy.

Next, in this example, the method 1300 includes the system 505 automatically recommending 1315, based on the assessed risk, computer network changes to reduce the assessed risk

Next, in this example, the method 1300 includes the system 505 providing 1320 one or more recommended computer network changes to reduce the assessed risk, enactment by the entity of at least one of the one or more of the recommended computer network changes to reduce the assessed risk to the entity.

The exemplary method 1300 also includes the system 505 determining 1325 that the entity has enacted at least a portion of the recommended computer network changes, and in response, automatically reassessing the cyber security risk of a cyber security failure in the computer network of the entity based on the enacted recommended computer network changes.

Next, the exemplary method 1300 includes the system 505 dynamically re-determining 1330, based on the reassessed risk of a cyber security failure in the computer network of the entity, the change or the setting to the at least one element of policy criteria of the cyber security policy.

FIG. 14 is a flowchart of an example method 1400. The method 1400 includes the system 505, based on the assessing of risk of the cyber security failure in the computer network of the entity, plotting 1405 one or more features of the entity and other members of a peer group of the entity, the plotting being configured to visually illustrate the risk of a cyber security failure in the computer network of the entity; and the automatically recommending of computer network changes being based on the plotting.

Next, the method 1400 includes the system 505, in response to the determining that the entity has enacted at least a portion of the recommended computer network changes, initiating 1410 the change or the setting to the at least one element of policy criteria of the cyber security policy.

Next, the method 1400 for the assessing of risk of the cyber security failure in the computer network of the entity includes the system 505, using 1415 a plurality of sophistication elements for the entity, a sophistication for the entity with respect to preventing the cyber security failure, the sophistication being one of features of the entity. Again, the sophistication relates to people, processes, and technology. The sophistication analysis as a whole attempts to quantify how strong a threat actor would be required to execute a successful security failure of the entity.

Next, the method 1400 for the assessing of risk of the cyber security failure in the computer network of the entity includes the system 505 assessing, using a plurality of motivation elements regarding the entity, a motivation of an actor to initiate the cyber security failure, the motivation being one of a plurality of features of the entity. In some embodiments motivation is a motivation of an actor (e.g., a hacker) to initiate a cyber security failure.

FIG. 15 is a flowchart of yet another example method 1500 for modifying a policy based on a cyber risk analysis. The method 1500 includes the system 505 assessing 1505, using a plurality of sophistication elements for the entity, a sophistication for the entity with respect to preventing the cyber security failure, the sophistication being one of a plurality of features of the entity; and assessing, using a plurality of motivation elements regarding the entity, a motivation of an actor to initiate the cyber security failure, the motivation being another one of the features of the entity. Again, the sophistication relates to people, processes, and technology. The sophistication analysis as a whole attempts to quantify how strong a threat actor would be required to cause a successful cyber failure.

Next, the method 1500 in various embodiments includes the system 505 calculating 1510 a composite score from a motivation score and a sophistication score, the motivation score representing the plurality of motivation elements, the sophistication score representing the plurality of sophistication elements.

To be sure, steps 1505 and 1510 include the collection of motivation and sophistication elements, converting these elements into mathematical representations (if needed), and processing these elements into scores using relevant algorithms.

In some embodiments, the method 1500 includes the system 505 creating 1515 an aggregate risk score of a portfolio of entities based on a plurality of motivation scores including the motivation score and a plurality of sophistication scores including the sophistication score; and benchmarking over time at least one of the sophistication score, the motivation score, the composite score, and the aggregate risk score.

Next, the method 1500 in some embodiments includes the system 505 identifying 1520 clusters of sophistication elements or motivation elements shared between two or more entities of the portfolio of entities, the clusters of sophistication elements or motivation elements being associated with an increase in risk of a cyber security failure in the computer network of the entity.

Next, the method 1500 in some instances includes the system 505 identifying 1525 additional sophistication elements or motivation elements for at least one of the two or more entities of the portfolio of entities that are not shared with the portfolio of entities, the additional sophistication elements or motivation elements being associated with another increase in the risk of a cyber security failure in the computer network of the entity; and generating recommendations for the at least one of the two or more entities of the portfolio of entities that will cause a decrease in the risk of a cyber security failure in the computer network of the entity.

According to some embodiments, the system 505 can be programmed with policy parameters. The system 505 can generate recommendations for the insurer based on the motivation and sophistication analysis of the entity. In some instances, the recommendation could be to deny a policy or terminate a policy if the entity has motivation or sophistication elements that are defined by the policy as being unacceptable or uninsurable.

According to some embodiments, the present disclosure can include systems and methods that utilize the vast array of information gathered by computer agents and provided by entities to discover circumstantial or indirect evidence about an entity that may affect the entity's assessed risk.

For context, data collected by the systems and methods of the present disclosure, such as system 505 (FIG. 5), may obtain a large amount of data (e.g., big data collection) that can include many types of data that directly reference, partially reference, or indirectly reference an entity. A direct reference is a reference to an entity that is confirmable, meaning that it is virtually certain that the entity is discussed or referenced by a particular data. An example would be a newspaper article.

A partial reference could include any data that mentions the entity, but references the entity in an incomplete manner. For example, an online review where the entity has been named, but the author did not spell the entity's name in an exact manner. Thus, the partial reference is a simple process to confirm whether the data is truly referencing the entity.

Data using an indirect reference may be more difficult to analyze. For example, a social media user may write a lengthy complaint about a particular entity, but the author may not want to name the entity directly. Through big data collection processes and circumstantial or indirect evidence analysis using cross referencing of the big data content, the system 505 can confirm that an entity is being referenced by the author. By way of example, suppose that the author is an employee of the entity and is writing a whistle blowing article about workplace behaviors of the entity. Using collected data, the system can cross reference the author's name and workplace with entity information stored in the system to determine or infer that the employee is describing their workplace.

As additional information and data are collected and stored by the system 505, the ability of the system 505 to cross reference data increases, which also increases the likelihood that circumstantial or indirect linkages will be determined and found useful for the diversity analyses described herein.

To be sure, these circumstantial evidentiary reviews may be utilized in risk assessment. If the circumstantial or indirect evidence is positive, the cyber risk may be decreased. Conversely, if the circumstantial or indirect evidence is negative, the cyber risk may be increased.

Also, in some embodiments, a relative strength of the cross referenced circumstantial or indirect evidence can be determine and utilized. For example, if the system cannot determine with certainty that the entity is implicated in the circumstantial or indirect evidence, or if the circumstantial or indirect evidence is negative or positive in nature, the system 505 can choose to ignore the circumstantial or indirect evidence within the diversity analysis or flag the entity for additional review.

FIG. 16 is a flowchart of an example method 1600 of the present disclosure. The method 1600 includes the system 505 assessing 1605 risk of a cyber security failure in a computer network of an entity, using a computer agent configured to collect information from at least publicly accessible Internet elements. The cyber risk includes a security failure (e.g., a cyber-attack, a privacy incident) of the entity.

The system 505 may query the entity for information, collect information from available online sources such as websites, corporate filings, news sources, other public record databases, and other resources. Additionally, data may be gathered from the entity's network using devices already present there or by placing a new data collecting device on the entity's network to gather more data. The data collecting device may be on the company's network and/or its periphery, and may collect and/or analyze the data, while also transmitting it to system 505. In this example, additional, proprietary data may be gleaned from a particular entity's network.

In various embodiments, a component of this review process includes a circumstantial or indirect data or information review for the entity. Thus, the method 1600 includes a sub-process that involves a step 1605-A of evaluating the collected information to obtain circumstantial or indirect information that is indicative of the entity. In one example, the process comprises reviewing the social media accounts of employees of the entity, as well as any other online resources linked to the employees. Another example includes searching trade journals or legal proceedings. In another example, the process utilizes data gathered during routine use of the system 505 in gathering data for direct cyber risk assessments and extracting circumstantial or indirect information therefrom.

Next, the sub-process comprises a step 1605-B of cross referencing data in the collected information to confirm or infer that the entity is referenced in the circumstantial or indirect information that is indicative of the entity being referenced in the circumstantial or indirect information.

The sub-process can also include a step 1605-C of at least one of increasing or decreasing the assessed risk if the circumstantial or indirect information is negative or positive.

Also, as mentioned above, strength of the circumstantial or indirect analysis can be utilized in some embodiments. For example, if the circumstantial or indirect analysis does not conclude that the entity referenced in the circumstantial or indirect data is the entity of the subject cyber risk analysis, but that it is highly likely that the entity is correct, the system 505 can weigh the circumstantial or indirect analysis aspect of the risk analysis by 80 percent. If the entity is later determined to be correct through additional data gathering, a weight of the circumstantial or indirect analysis can be increased to 100 percent.

Thus, in some embodiments, the circumstantial or indirect analysis can be periodically executed to refine the cyber risk analyses of the present disclosure. In one embodiment, the circumstantial or indirect analysis is executed during re-assessment and/or re-determining periods described herein. In other embodiments, the circumstantial or indirect analysis is executed and/or re-executed at other intervals.

By way of example, if the risk analysis calculates a circumstantial score of seven for the entity (where scores fall in a range of zero to 10), and the system 505 has a certainty level of 80 percent, the score would be reduced to 5.6.

The exemplary method 1600 also includes the system 505 automatically determining 1610, based on the assessed risk, a change or a setting to at least one element of policy criteria of a cyber security policy. In some embodiments, the one or more elements of policy criteria involve a term or condition of a cyber policy. In one embodiment, the cyber policy includes a cyber security insurance policy.

Next, in this example, the method 1600 includes the system 505 automatically recommending 1615, based on the assessed risk, computer network changes to reduce the assessed risk.

Next, in some instances, the method 1600 includes the system 505 providing 1620 one or more recommended computer network changes to reduce the assessed risk, enactment by the entity of at least one of the one or more of the recommended computer network changes to reduce the assessed risk to the entity.

The exemplary method 1600 also includes the system 505 determining 1625 determining that the entity has enacted at least a portion of the recommended computer network changes, and in response, automatically reassessing the cyber security risk of a cyber security failure in the computer network of the entity based on the enacted recommended computer network changes.

Next, the exemplary method 1600 includes the system 505 dynamically re-determining 1630, based on the reassessed risk, the change or the setting to the at least one element of policy criteria of the cyber security policy.

According to some embodiments, the present disclosure can be adapted to use gathered information for an entity (such as an entity profile created from information gathered from public and private resources) and model a disaster scenario against the gathered information to determine an economic and/or cyber security impact of the disaster scenario on the entity, and in some instances specifically related to the network of the entity.

Examples of disaster scenarios include, but are not limited to DDOS attacks, mass data infiltrations, or other cyber attacks, as well as disasters from natural events such as floods, fires, earthquakes or other physical phenomena. Other example disaster scenarios include risks associated with financial aspects, and indirect costs associated with cyber breaches, effects on smaller companies (for instance, loss of customers to competitors due to a cyber breach, for example, could cause a smaller company to seek bankruptcy protection), and reputational damage.

Referring back to FIG. 5, the system 505 can model the entity network, a proposed disaster scenario, and generate prospective damage calculations. The system can also generate recommendations for remediating issues that increase the prospective damage calculations. For example, if an entity has a physical server room where its data is stored but does not have a backup cloud service that is replicating the devices in the physical server room, the system can model a fire disaster that affects 75% of the devices in the physical server room taking them offline. With no backup cloud service, the data on these devices may be unrecoverable. The system then generates prospective damage calculations for the disaster event. The system could also calculate a second prospective damage calculation that would model the same event with the exception that the entity did utilize a backup cloud service.

If the system 505 determines that no backup cloud service is being utilized by an entity, the system 505 can use a ruleset to determine that selection and use of a backup cloud service would result in improvements to the network of the entity that mitigate risk and reduce the likelihood that a disaster event would create large damages.

In some embodiments, the system 505 provides a disaster modeling service or module 555 that allows a user to build various disaster scenarios, which would include specifying any negative outcomes of the disaster scenarios. For example, the user could create a disaster scenario that models a typical DDOS attack against a network.

This information could be gathered from the numerous resources that are interrogated by the system 505 when evaluating information that is directly or indirectly related to the entity. Again, these data gathering aspects are discussed in greater detail supra.

In some embodiments, the disaster modeling module 555 can also intelligently select and create or suggest disaster scenarios based on entity information that the system stores in the database. For example, if it is determined that 60 entities in the database exist and that a subset of these entities (such as six entities) use a particular cloud computing services provider, e.g., Amazon Web Services (AWS), the system can detect this commonality and suggest that a disaster scenario related to AWS be created and modeled against profiles/information for the subset of entities.

In some embodiments, the system 505 can obtain the scenarios based on selections or other inputs from end users of the system 505 and outcomes/damages produced by modeling of disaster scenarios. The system 505 can analyze the user created scenarios and output of the modeling and determine general categories of interest. For example, based on information collected the system 505 can determine or infer that users are concerned about issues with email systems because users are frequently modeling attacks against email systems. Based on this and/or other data collection described herein, the disaster models can be updated.

Using the direct, circumstantial, and/or inferential information gathered by the system 505, as well as the information produced by modeling disaster scenarios, the system 505 can generate and/or update disaster modeling or provide suggestions for how disaster models can be improved. For example, if a user is creating a modeling scenario for testing DNS server vulnerability and the user has inadvertently failed to include all their DNS servers in the modeling scenario, the system 505 can identify this error and suggest to the user that the modeling scenario can be improved by inclusion of missing information.

In some embodiments, the system 505 can suggest disaster models that the user can select from. The user can use the disaster model as-is or tailor the disaster model as desired. These tailored aspects can be analyzed by the system 505 to create alternative or new disaster models.

In some embodiments, one or more levers may be included, e.g., for the disaster model, which the user can utilize for making selections concerning disaster scenarios. Various embodiments can use those selections as feedback input into the process and learn (e.g., utilizing machine learning or the like) based on the various inputs in order to update the scenarios and system. For example, the system may learn based on the levers and selections that an entity has been infected with a bug, or an exploit is affecting the entity more commonly than others. Learning, using machine learning, etc., from this input, the disaster scenarios can be updated based on the learning, e.g., to improve the scenarios and tailor them more for the particular entity.

It will be understood that the disaster models can be used to improve capacity management where a cyber risk company is interested in entity solvency. The cyber risk company desires to evaluate adverse outcomes for portfolio risk for possible payouts. Moreover, these disaster models allow cyber risk companies to forecast budgeting and reserves, especially when large damages can occur. The methods and systems described herein provide an actionable means for predicting and potentially remediating damages from likely disaster events.

FIG. 17A-B collectively illustrate a flowchart of an example method of the present disclosure. This method is similar to the method of FIG. 16 with the exception that the method includes various disaster modeling aspects.

The method includes the system 505 assessing 1705 risk of a cyber security failure in a computer network of an entity, using a computer agent configured to collect information from at least publicly accessible Internet elements. The cyber risk includes a security failure (e.g., a cyber-attack, a privacy incident) of the entity.

As mentioned above, the data gathering aspect of the system 505 allows for continual and periodic collection of data over time, as well as data mining from disaster modeling scenarios, as described in greater detail below.

The system 505 may query the entity for information, collect information from available online sources such as websites, corporate filings, news sources, other public record databases, and other resources. Additionally, data may be gathered from the entity's network using devices already present there or by placing a new data collecting device on the entity's network to gather more data. The data collecting device may be on the company's network and/or its periphery, and may collect and/or analyze the data, while also transmitting it to system 505. In this example, additional, proprietary data may be gleaned from a particular entity's network.

In various embodiments, a component of this review process includes a circumstantial or indirect data or information review for the entity. Thus, the method 1700 includes a sub-process that involves a step 1705-A of evaluating the collected information to obtain circumstantial or indirect information that is indicative of the entity. In one example, the process comprises reviewing the social media accounts of employees of the entity, as well as any other online resources linked to the employees. Another example includes searching trade journals or legal proceedings. In another example, the process utilizes data gathered during routine use of the system 505 in gathering data for direct cyber risk assessments and extracting circumstantial or indirect information therefrom.

Next, the sub-process comprises a step 1705-B of cross referencing data in the collected information to confirm or infer that the entity is referenced in the circumstantial or indirect information that is indicative of the entity being referenced in the circumstantial or indirect information.

The sub-process can also include a step 1705-C of at least one of increasing or decreasing the assessed risk if the circumstantial or indirect information is negative or positive.

The exemplary method 1700 also includes the system 505 automatically determining 1710, based on the assessed risk, a change or a setting to at least one element of policy criteria of a cyber security policy. In some embodiments, the one or more elements of policy criteria involve a term or condition of a cyber policy. In one embodiment, the cyber policy includes a cyber security insurance policy.

Next, in this example, the method 1700 includes the system 505 automatically recommending 1715, based on the assessed risk, computer network changes to reduce the assessed risk.

Next, in some instances, the method 1700 includes the system 505 providing 1720 one or more recommended computer network changes to reduce the assessed risk, enactment by the entity of at least one of the one or more of the recommended computer network changes to reduce the assessed risk to the entity.

The exemplary method 1700 also includes the system 505 determining 1725 that the entity has enacted at least a portion of the recommended computer network changes, and in response, automatically reassessing the cyber security risk of a cyber security failure in the computer network of the entity based on the enacted recommended computer network changes.

Next, the exemplary method 1700 includes the system 505 dynamically re-determining 1730, based on the reassessed risk, the change or the setting to the at least one element of policy criteria of the cyber security policy.

In some embodiments, the method comprises steps for performing disaster modeling against a profile or database information obtained for the entity and/or the computer network. In FIG. 17B, the method includes a step 1735 of generating a disaster scenario that comprises elements of a disaster event. This step can be performed by the system 505 when, for example, it generates disaster scenario or optimized disaster scenarios using prior outcomes and disaster scenario modeling. In other embodiments, the end user can create a model. The system 505 can improve or provide suggestions for the user created model in some embodiments.

It will be understood that an element of the disaster scenario could include any attributes that the user or system desires to test against the computer network. For example, the disaster scenario could include one or more of a major security or privacy breach of key computer systems, total loss of power, total loss of internet connectivity, total loss of cloud services, total loss of data backup, flood, wind, and/or earthquake damage to computing devices, employee strike, or other disaster attributes that the user wants to test against.

The profile of the computing network would include relevant information such as network components, disaster plans, backup services, employee data, cyber security policies, and other determined attributes of the entity (again, either directly or indirectly known).

In some embodiments, the method includes a step 1740 of modeling the disaster scenario against a profile of the computer network and the entity.

According to some embodiments, the method can include a step 1745 of determining theoretical damage based on the modeling, as well as a step 1750 of updating the cyber security policy or a network change to mitigate the theoretical damage. By way of example, the system 505 can generate a recommendation that the entity purchase or enhance their firewall or security protocols if the disaster scenario included network penetration testing that uncovered a security flaw in the computer network. Another recommendation could be for the entity to use AWS for their hosting or to implement or utilize other services in order to recover with less downtime if a disaster scenario uncovers that a current service had undue delay times for the entity in the event of a disaster. For example, the entity may commit to customers that certain content or services are always accessible. Any downtime of the service or content due to latency in restoration of the computing network or other key assets during or after a disaster could create economic and/or other damages.

In some embodiments, the method can comprises additional steps such as step 1755 of incorporating outcome data of the modeling into the re-determining of the risk of a cyber security failure in the computer network. Another method step 1760 can include generating recommended suggestions for the computer network relative to the disaster scenario and based on the collected information obtained for the computer network and the entity or a step 1765 of generating optimized or improved disaster scenarios based on outcomes of disaster scenario modeling of a plurality of computer networks, as discussed in greater detail above.

FIG. 18 is a diagrammatic representation of an example machine in the form of a computer system 1, within which a set of instructions for causing the machine to perform any one or more of the methodologies discussed herein may be executed. In various example embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, a portable music player (e.g., a portable hard drive audio device such as an Moving Picture Experts Group Audio Layer 3 (MP3) player), a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The example computer system 1 includes a processor or multiple processor(s) 5 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), and a main memory 10 and static memory 15, which communicate with each other via a bus 20. The computer system 1 may further include a video display 35 (e.g., a liquid crystal display (LCD)). The computer system 1 may also include an alpha-numeric input device(s) 30 (e.g., a keyboard), a cursor control device (e.g., a mouse), a voice recognition or biometric verification unit (not shown), a drive unit 37 (also referred to as disk drive unit), a signal generation device 40 (e.g., a speaker), and a network interface device 45. The computer system 1 may further include a data encryption module (not shown) to encrypt data.

The disk drive unit 37 includes a computer or machine-readable medium 50 on which is stored one or more sets of instructions and data structures (e.g., instructions 55) embodying or utilizing any one or more of the methodologies or functions described herein. The instructions 55 may also reside, completely or at least partially, within the main memory 10 and/or within the processor(s) 5 during execution thereof by the computer system 1. The main memory 10 and the processor(s) 5 may also constitute machine-readable media.

The instructions 55 may further be transmitted or received over a network (e.g., network 105B or network 520, see FIG. 1 and FIG. 5, respectively) via the network interface device 45 utilizing any one of a number of well-known transfer protocols (e.g., Hyper Text Transfer Protocol (HTTP)). While the machine-readable medium 50 is shown in an example embodiment to be a single medium, the term “computer-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database and/or associated caches and servers) that store the one or more sets of instructions. The term “computer-readable medium” shall also be taken to include any medium that is capable of storing, encoding, or carrying a set of instructions for execution by the machine and that causes the machine to perform any one or more of the methodologies of the present application, or that is capable of storing, encoding, or carrying data structures utilized by or associated with such a set of instructions. The term “computer-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic media, and carrier wave signals. Such media may also include, without limitation, hard disks, floppy disks, flash memory cards, digital video disks, random access memory (RAM), read only memory (ROM), and the like. The example embodiments described herein may be implemented in an operating environment comprising software installed on a computer, in hardware, or in a combination of software and hardware.

One skilled in the art will recognize that the Internet service may be configured to provide Internet access to one or more computing devices that are coupled to the Internet service, and that the computing devices may include one or more processors, buses, memory devices, display devices, input/output devices, and the like. Furthermore, those skilled in the art may appreciate that the Internet service may be coupled to one or more databases, repositories, servers, and the like, which may be utilized in order to implement any of the embodiments of the disclosure as described herein.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present technology has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the present technology in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the present technology. Exemplary embodiments were chosen and described in order to best explain the principles of the present technology and its practical application, and to enable others of ordinary skill in the art to understand the present technology for various embodiments with various modifications as are suited to the particular use contemplated.

Aspects of the present technology are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present technology. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present technology. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular embodiments, procedures, techniques, etc. in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details.

Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” or “according to one embodiment” (or other phrases having similar import) at various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Furthermore, depending on the context of discussion herein, a singular term may include its plural forms and a plural term may include its singular form. Similarly, a hyphenated term (e.g., “on-demand”) may be occasionally interchangeably used with its non-hyphenated version (e.g., “on demand”), a capitalized entry (e.g., “Software”) may be interchangeably used with its non-capitalized version (e.g., “software”), a plural term may be indicated with or without an apostrophe (e.g., PE's or PEs), and an italicized term (e.g., “N+1”) may be interchangeably used with its non-italicized version (e.g., “N+1”). Such occasional interchangeable uses shall not be considered inconsistent with each other.

Also, some embodiments may be described in terms of “means for” performing a task or set of tasks. It will be understood that a “means for” may be expressed herein in terms of a structure, such as a processor, a memory, an I/O device such as a camera, or combinations thereof. Alternatively, the “means for” may include an algorithm that is descriptive of a function or method step, while in yet other embodiments the “means for” is expressed in terms of a mathematical formula, prose, or as a flow chart or signal diagram.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It is noted at the outset that the terms “coupled,” “connected”, “connecting,” “electrically connected,” etc., are used interchangeably herein to generally refer to the condition of being electrically/electronically connected. Similarly, a first entity is considered to be in “communication” with a second entity (or entities) when the first entity electrically sends and/or receives (whether through wireline or wireless means) information signals (whether containing data information or non-data/control information) to the second entity regardless of the type (analog or digital) of those signals. It is further noted that various figures (including component diagrams) shown and discussed herein are for illustrative purpose only, and are not drawn to scale.

While specific embodiments of, and examples for, the system are described above for illustrative purposes, various equivalent modifications are possible within the scope of the system, as those skilled in the relevant art will recognize. For example, while processes or steps are presented in a given order, alternative embodiments may perform routines having steps in a different order, and some processes or steps may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or sub-combinations. Each of these processes or steps may be implemented in a variety of different ways. Also, while processes or steps are at times shown as being performed in series, these processes or steps may instead be performed in parallel, or may be performed at different times.

While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. The descriptions are not intended to limit the scope of the invention to the particular forms set forth herein. To the contrary, the present descriptions are intended to cover such alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims and otherwise appreciated by one of ordinary skill in the art. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments. 

1. A method, comprising: assessing risk of an entity, using a computer agent configured to collect information from at least publicly accessible Internet elements, wherein the assessing of risk comprises: generating a disaster scenario that comprises elements of a disaster event; modeling the disaster scenario against a profile of the entity; and determining theoretical damage based at least in part on the modeling; and automatically recommending, based at least in part on the assessed risk, changes to reduce the assessed risk to mitigate the theoretical damage.
 2. The method of claim 1, wherein the assessed risk comprises a cyber security failure risk in a computer network of the entity, and the changes include one or more of: an update to a cyber security policy, a setting to the cyber security policy, a network change, and/or a network setting.
 3. The method of claim 1, further comprising: determining that the entity has enacted at least a portion of the automatically recommended changes, and in response, automatically reassessing the risk of the entity; and dynamically re-determining, based at least in part on the reassessed risk, an update, a setting, or both to a cyber security policy.
 4. The method of claim 3, wherein outcome data of the modeling is incorporated into the reassessed the risk of the entity.
 5. The method of claim 2, further comprising generating recommended suggestions for the computer network relative to the disaster scenario and based at least in part on the collected information obtained for the computer network and the entity.
 6. The method of claim 1, further comprising generating optimized or improved disaster scenarios based at least in part on outcomes of disaster scenario modeling of a plurality of computer networks.
 7. The method of claim 1, further comprising: providing a user interface for receiving selections from an end use of disaster events from a plurality of disaster events; and based at least in part on the selections, generating an updated disaster scenario.
 8. The method of claim 7, wherein the selections are inputs for machine learning and generating the updated disaster scenario is based, at least in part, on the machine learning.
 9. The method of claim 2, wherein the cyber security failure comprises a cyber attack, a privacy incident involving sensitive information, or both.
 10. The method of claim 2, wherein the cyber security policy includes: a cyber security policy from another entity; a product warranty for first and/or third party costs that the entity purchases from at least one of a networking, security product, and services provider; or both.
 11. The method of claim 1, wherein the computer agent is further configured to perform: collecting information from a computer network of the entity, analyzing information from the computer network of the entity, or both.
 12. A system, comprising: one or more processors configured to: assess risk of an entity, using a computer agent configured to collect information from at least publicly accessible Internet elements, wherein to assess the risk comprises to: generate a disaster scenario that comprises elements of a disaster event; model the disaster scenario against a profile of the entity; and determine theoretical damage based at least in part on the modeling of the disaster scenario; and automatically recommend, based at least in part on the assessed risk, changes to reduce the assessed risk to mitigate the theoretical damage; and one or more memories coupled to the one or more processors, configured to provide the one or more processors with instructions.
 13. The system of claim 12, wherein the assessed risk comprises a cyber security failure risk in a computer network of the entity, and the changes include one or more of: an update to a cyber security policy, a setting to the cyber security policy, a network change, and/or a network setting.
 14. The system of claim 12, wherein the one or more processors are further configured to: determine that the entity has enacted at least a portion of the automatically recommended changes, and in response, automatically reassessing the risk of the entity; and dynamically re-determine, based at least in part on the reassessed risk, an update, a setting, or both to a cyber security policy.
 15. The system of claim 14, wherein outcome data of the modeling is incorporated into the reassessed the risk of the entity.
 16. The system of claim 13, wherein the one or more processors are further configured to generate recommended suggestions for the computer network relative to the disaster scenario and based at least in part on the collected information obtained for the computer network and the entity.
 17. The system of claim 12, wherein the one or more processors are further configured to generate optimized or improved disaster scenarios based at least in part on outcomes of disaster scenario modeling of a plurality of computer networks.
 18. The system of claim 12, wherein the one or more processors are further configured to: provide a user interface for receiving selections from an end use of disaster events from a plurality of disaster events; and based at least in part on the selections, generate an updated disaster scenario.
 19. The system of claim 18, wherein the selections are inputs for machine learning and generating the updated disaster scenario is based, at least in part, on the machine learning.
 20. The system of claim 13, wherein the cyber security failure comprises a cyber attack, a privacy incident involving sensitive information, or both.
 21. The system of claim 13, wherein the cyber security policy includes: a cyber security policy from another entity; a product warranty for first and/or third party costs that the entity purchases from at least one of a networking, security product, and services provider; or both.
 22. The system of claim 12, wherein the computer agent is further configured to perform: collecting information from a computer network of the entity, analyzing information from the computer network of the entity, or both. 